Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0429

reference: 413-tree-1
name: 0429
tree-preservation-order: undefined
413-tpo-1
uprn
address-text
point: POINT (-1.022172 50.890921)
geometry: MULTIPOLYGON (((-1.022116 50.890915,-1.022118 50.890926,-1.022126 50.890936,-1.022138 50.890944,-1.022154 50.890950,-1.022172 50.890952,-1.022189 50.890950,-1.022205 50.890945,-1.022218 50.890937,-1.022226 50.890927,-1.022229 50.890916,-1.022227 50.890905,-1.022219 50.890895,-1.022206 50.890887,-1.022191 50.890882,-1.022173 50.890880,-1.022156 50.890881,-1.022140 50.890886,-1.022127 50.890894,-1.022119 50.890904,-1.022116 50.890915)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL